<html><head><title>
WHIFF -- WSGI/HTTP INTEGRATED FILESYSTEM FRAMES 
</title>

<link rel="icon" type="image/jpg" href="whiff.jpg">
<link rel="stylesheet" href="style.css" type="text/css">

</head><body class="all">
<table cellpadding="10">
<tbody><tr> 
   <td align="center" valign="top"> 
	<!-- lhs -->
	<table bgcolor="black">
	<tbody><tr><td> <img src="whiff.jpg" height="200" width="230"></td> </tr>
	</tbody></table>
   </td>
   <td align="center" valign="top"> 
	<!-- rhs -->
	<table cellpadding="0">
	<tbody><tr><td align="center">
		<div class="title">
			<em>WHIFF -- WSGI/HTTP INTEGRATED FILESYSTEM FRAMES </em>
			<h3>Whiff Package pointers</h3> 
		</div>
	</td></tr>
	<tr><td>
	   <div class="summary"> <b><em>WHIFF
is an infrastructure for easily building complex Python/WSGI Web
applications by combining smaller and simpler WSGI components organized
within file system trees.</em></b> </div>
	</td></tr>
	<tr><td>
		<div class="body">

This is an "index" page with pointers to information about the WHIFF package.
<p>
To <b>DOWNLOAD WHIFF</b> go to the
<a href="http://sourceforge.net/projects/whiff/">WHIFF project information page
at http://sourceforge.net/projects/whiff and follow the download instructions.</a>
<p>
To <b>GET THE LATEST WHIFF</b> clone the 
<a href="http://aaron.oirt.rutgers.edu/cgi-bin/whiffRepo.cgi">
WHIFF Mercurial repository
located at http://aaron.oirt.rutgers.edu/cgi-bin/whiffRepo.cgi</a>.
<p>
To <b>READ ABOUT WHIFF</b> 
<a href="http://aaron.oirt.rutgers.edu/myapp/docs/W.intro">
view the WHIFF documentation at http://aaron.oirt.rutgers.edu/myapp/docs/W.intro</a>.
<p>
To <b>PLAY WITH WHIFF</b>
<a href="http://aaron.oirt.rutgers.edu/myapp/docs/W1300.testAndDemo">
try the demos listed in the demos page at http://aaron.oirt.rutgers.edu/myapp/docs/W1300.testAndDemo</a>.

<h2>Why WHIFF?</h2>

WHIFF (WSGI HTTP Integrated Filesystem Frames) is intended to make it easier to
create, deploy, and maintain large and complex Python based WSGI Web applications.
I created WHIFF to address complexity issues I encounter when creating and fixing
sophisticated Web applications which include complex database interactions and
dynamic features such as AJAX (Asynchronous JavaScript and XML).
<p>
The primary tools which reduce complexity are an infrastructure for <b>managing web
application name spaces</b>, a <b>configuration template language</b> for wiring named components
into an application, and an 
<b>applications programmer interface for accessing named components</b> from Python and 
javascript modules.
<p>
All supporting conventions and tools offered by WHIFF are optional.
WHIFF is designed to work well with other modules conformant to the WSGI
(Web Service Gateway Interface) standard. Developers and designers are
free to use those WHIFF tools that work for them and ignore or replace the others.
</p><p>
WHIFF does not provide a "packaged cake mix" for baking a web application.
Instead WHIFF is designed to provide a set of ingredients which can be
easily combined to make web applications (with no need to refine 
your own sugar or mill your own wheat).

</td>
</tr>
</table>

</td>
</tr>
</table>

</body></html>